Languguage OS 2

home *** CD-ROM | disk | FTP | other *** search

/ Languguage OS 2 / Languguage OS II Version 10-94 (Knowledge Media)(1994).ISO / language / dino / dino_bot.1 / source / install / messages.h < prev

Wrap

Text File | 1991-06-14 | 20.0 KB | 481 lines

/* Copyright, 1990, Regents of the University of Colorado */ char *messages[] = { /* 0 */ "\n Welcome to the DINO Automated Installer.\n\n\ This tool can be used either to create a new DINO installation\n\ or to update an existing installation. In the first case, it\n\ will create a generic installation roughly tailored to your\n\ parallel machines. If you want more control over how DINO\n\ works or your parallel machine requires non-standard (special)\n\ shell commands to access it, you will have to modify the\n\ installation produced by this tool by hand. See the installation\n\ section of the DINO Manual for information on this.\n\n\ In the second case, this tool should completely update a DINO\n\ installation without changing the local configuration. The\n\ only exception to this would be the case in which an update\n\ changes the method used to configure DINO. If this is the case,\n\ there should be information in the \"README\" file about it.\n\n\ Enter a \"Q\" to quit now; just hit return to continue ==>", /* 1 */ " WARNING: DINO is unable to find the environment variable\n\ \"ARCHTYPE\". You must have this variable set to the architecture\n\ of the machine you are on for DINO to run properly. See the user\n\ section of the DINO User's Manual for more information on this. In\n\ addition, this suggests that you do not have your path set properly.\n\ You might want to check your path set-up procedure against that\n\ described in the Manual.\n\n\ Continuing with the DINO installation.\n\n\n", /* 2 */ " DINO has found both source files for the actual compiler as well as\n\ an existing executable. However, the source files are newer than\n\ the executable and DINO can not find a Pascal compiler in its path.\n\ DINO needs that compiler if it is to update the executable. You\n\ can either continue (and DINO will not update the executable) or\n\ you can quit the Automated Installer, fix the path, and restart.\n\ On OS4.x installations, the Pascal compiler should be in\n\ \"/usr/lang\".\n\n\ \n Enter a \"Q\" to quit now; just hit return to continue ==>", /* 3 */ " DINO has not found an executable for the actual compiler. DINO\n\ can generate that executable from sources which should have been\n\ included in your distribution. However, DINO needs a Pascal\n\ compiler to do that and has not found one in its path. DINO needs\n\ that compiler to continue. Please change dino's path to include\n\ that compiler. On OS4.x installations, the Pascal compiler\n\ should be in \"/usr/lang\"\n\n\ When you have fixed this problem, run \"install\" again.\n\n", /* 4 */ " DINO has found a copy of \"dino.init\" in bin/local that is\n\ malformed. The \"Dmachs\" environment variable is not defined\n\ properly. Please fix this file (or delete it if it should not\n\ be there). DINO assumes that this is an update if it finds an\n\ existing copy of \"dino.init\" and preserves the system configuration\n\ in that file. Otherwise DINO assumes this is a new installation.\n\n\ When you have fixed this problem, run \"install\" again.\n\n", /* 5 */ " DINO has found a copy of \"dino.init\" in bin/local that is\n\ not set up properly. Either the \"Dmachs\" environment variable\n\ is not defined or machine specific comments are missing or\n\ malformed. Please fix this file (or delete it if it should not\n\ be there). DINO assumes that this is an update if it finds an\n\ existing copy of \"dino.init\" and preserves the system configuration\n\ in that file. Otherwise DINO assumes this is a new installation.\n\n\ When you have fixed this problem, run \"install\" again.\n\n", /* 6 */ " DINO has found an existing \"dino.init\" file so it assumes\n\ that this is an update as opposed to an initial installation.\n\ DINO will go ahead and install the new files, preserving the\n\ present configuration.\n\n\ \n Proceed with the installation process??\n\n", /* 7 */ " DINO has not found an existing \"dino.init\" file so it\n\ assumes that this is an initial installation as opposed to\n\ an update. DINO assumes that you want to configure this\n\ installation for one or more parallel machines. DINO will\n\ ask you a series of questions for each machine. The answers\n\ will be used to set up this installation. You must answer\n\ questions for all the machines at one setting if you want to\n\ have the installation done automatically. Once you start the\n\ actual installation process, the only way you can change it\n\ is to delete the \"dino.init\" file and start all over or to\n\ modify the \"dino.init\" file by hand.\n\n\ Enter a \"Q\" to quit now; just hit return to continue ==>", /* 8 */ "\n\n Please answer the following questions for machine #", /* 9 */ " (if you\n\ want to quit, just hit return instead of answering the question):\n\n\ What is the (virtual) name of this parallel machine? The\n\ virtual name is the name you assign to it. Normally it is the\n\ same as the real name for a remote machine. We suggest \"sim\"\n\ for a simulator and \"sun\" for a distributed sun machine, but\n\ it is completely your choice.\n\n\ ==> ", /* 10 */ "\n\n What type of machine is ", /* 11 */ "? The allowable\n\ types are:\n\n\ s -- Intel iPSC1 simulator\n\ S -- Intel iPSC2 simulator\n\ 1 -- Intel iPSC1\n\ 2 -- Intel iPSC2\n\ 8 -- Intel i860 version of the iPSC2\n\ G -- distributed sun machine\n\n\ Enter an \"s\", an \"S\", a \"1\", a \"2\", an \"8\", or a \"G\"\n\n\ ==> ", /* 12 */ "\n If you want to quit the Automated Installer, enter a \"Q\"\n\ now; hit return to start machine #", /* 13 */ " over; or enter a \"Y\"\n or an \"N\" ==>\n", /* 14 */ "\n (You should enter either a \"Y\", an \"N\",\n\ or a return (to quit).)\n\n", /* 15 */ " either does not exist or is something other than a regular file.\n\ If you want to quit the Automated Installer, enter a \"Q\" now;\n\ If you want to start machine #", /* 16 */ " over, enter a \"R\" now;\n\ otherwise just hit return to reenter the library name ==>", /* 17 */ "? Normally for a remote\n\ machine, this would be the name, but you may need additional\n\ parts of the name on your network.\n\n ==> ", /* 18 */ "\n\n Do you want the Automated Installer to attempt to install\n\ the back end of DINO on ", /* 19 */ "? If you respond with a \"Y\", DINO\n\ will try to do the installation on ", /* 20 */ " automatically. Failing\n\ that, DINO will provide you with a simple manual method for\n\ installing the back end. If you respond with a \"N\", DINO\n\ will configure ", /* 21 */ " so that it always stops after the\n\ intermediate C files are generated.\n\n", /* 22 */ "\n\n Is the sun filesystem that the users' home directories are\n\ in cross-mounted to ", /* 23 */ "\n\n Is the directory which is the user's home directory on the\n\ sun filesystem also the home directory for the same user\n\ on ", /* 24 */ "\n You must designate one of them as the default machine -- that is,\n\ the machine that DINO will compile code for if the user does not\n\ specify a particular machine.\n\n", /* 25 */ "\n\n You have said that there are directories that are cross-mounted to\n", /* 26 */ " also cross-mounted? If it is, DINO can directly put the necessary\n\ files for the back end in that directory instead of using an \"rcp\"\n\ to do it.\n\n", /* 27 */ "\n Is there another directory that is cross-mounted that you want the\n\ back end of DINO installed on? ", /* 28 */ " will have to have\n\ write permission in that directory for this to work.\n\n", /* 29 */ "\n\n What is the full path name for that directory?\n\n ==> ", /* 30 */ " that you want the back end of DINO installed in? For\n\ DINO to actually do the installation, either ", /* 31 */ " must have a\n\ login there and write permission in that directory. (If\n\ that is not the case, enter \"none\" and DINO will set you\n\ up for a manual installation.)\n\n\ ==> ", /* 32 */ " until this problem is fixed. You can (1) quit the Automated\n\ Installer and fix the problem, (2) continue but skip this parallel\n\ machine, or (3) have DINO set you up for a manual installation for\n\ this machine. If you chose the latter, you will have to copy files\n\ to the machine by hand and use \"make\" to set them up. You will\n\ be given instructions on how to do this.\n\n\ If you want to quit the Automated Installer, enter a \"Q\" now;\n\ if you want DINO to set up a manual installation, enter an \"M\" now;\n\ otherwise just hit return to start machine #", /* 33 */ "\n At this point you have three choices: (1) You can quit the\n\ Automated Installer and fix things so that there is a user who has\n\ the correct permissions, (2) you can continue but skip this parallel\n\ machine, or (3) you can have DINO set you up for a manual\n\ installation for this machine. If you chose the latter, you will\n\ have to copy files to the machine by hand and use \"make\" to set\n\ them up. You will be given instructions on how to do this.\n\n\ If you want to quit the Automated Installer, enter a \"Q\" now;\n\ if you want DINO to set up a manual installation, enter an \"M\" now;\n\ otherwise just hit return to start machine #", /* 34 */ " DINO has finished the automated part of this installation. There\n\ are a number of things that you should be aware of in order to use DINO\n\ properly:\n\n\ A copy of the DINO User's Manual can be found in:\n\n\ ", /* 35 */ "/doc\n\n\ To produce a dvi file, change to that directory and type \"make\".\n\ Then use whatever TeX output program your installation has to print\n\ TeX documents (ours is \"dvips\"). If you are unable to use the\n\ LaTeX format, contact \"dino@cs.colorado.edu\" and we can provide\n\ you with a hard copy.\n\n\ To use DINO, you must have the \"ARCHTYPE\" variable set properly.\n\ More information can be found about this in the DINO User's Manual.\n\n\ To use DINO, you must also have your path set properly. For this\n\ installation, your path must include the following directory:\n\n\ ", /* 36*/ "/bin/${ARCHTYPE}\n\n\ More information can be found in the DINO User's Manual.\n\n\ (Hit return to continue.)", /* 37*/ " To use this machine, the user must have the \"ARCHTYPE\" variable ON\n\ THIS MACHINE set properly. The ARCHTYPE variable on this machine\n\ must be set to \"", /* 38*/ "\". More information can be found about this\n\ in the DINO User's Manual.\n\n\ Again, the path on this machine must also be set properly. The\n\ users' path must include the directory:\n\n\ ", /* 39*/ "/bin/${ARCHTYPE}\n\n\ More information can be found in the DINO User's Manual.\n\n", /* 40*/ " DINO did not completely install this machine. Instead, it created\n\ a directory on the sun that contains all the files needed on the\n\ parallel machine. You need to do two things: first, copy (recursively)\n\ every entry in the directory\n\n\ ", /* 41*/ " to the following directory on the parallel machine:\n\n\ ", /* 42*/ " When you are finished, you will have duplicated the trees in the\n\ \"", /* 43*/ "\" directory (located on the sun) on the parallel machine.\n\ Second, log onto the parallel machine, change to the directory:\n\n\ ", /* 44*/ " and type \"make\". If DINO has set it up correctly, this should\n\ complete the installation.\n\n", /* 45*/ " (Hit return to continue.)", /* 46*/ " Although DINO defined the back end to this machine, it did not\n\ install it because you said that you wanted DINO to stop after\n\ generating the intermediate C files. Presumably you did this either\n\ because you only want to run the first stage of the compiler or\n\ because you want to install the second stage completely by hand. In\n\ the latter case, please read the Installation Section of the DINO\n\ User's Manual carefully first.\n\n\ (Hit return to continue.)", /* 47*/ " This is a local parallel machine (it also runs on the sun). It\n\ should be properly installed and there is nothing additional the\n\ user needs to do to have it run correctly.\n\n\ (Hit return to continue.)", /* 48*/ " The way DINO is installed here assumes that a user wanting to use a\n\ remote parallel machine has a login on that machine that is the same\n\ as his or her login on the sun and, in addition, that the remote\n\ parallel machine trusts the sun that the first part of the DINO\n\ compiler is being run on. It is possible to set DINO up to do more\n\ complicated arrangements, but this must be done by hand. If you are\n\ interested in this, see the Installation Section of the DINO User's\n\ Manual.\n\n\ In addition, DINO has been installed with in essentially a \"plain\n\ vanilla\" configuration. In particular, we have just used the\n\ standard libraries and options for the compilation on the remote\n\ parallel machines. If you want something other than this (if, for\n\ example, your iPSC2 has vector nodes that you wish to compile for)\n\ you will have to change things by hand. If you named your machine\n\ \"frank\", there will be a configuration file named \"dino2.frank\"\n\ in the directory \"bin/local\" on that machine that you need to edit.\n\ Consult the Installation Section in the DINO User's Manual for more\n\ information on this.\n\n\ (Hit return to continue.)", /* 49*/ " You have completed this setup on a ", /* 50*/ " architecture. If you\n\ also want DINO to work on ", /* 51*/ " machines, you must log onto a\n\ machine with that architecure and do the installation process all\n\ over. This time, however, DINO will treat the installation as an\n\ update and ask only a few questions.\n\n\ If you want to completely redo the installation at this point, you\n\ should erase all the files found in the \". . .bin/local\"\n\ directories, both on the sun and on the parallel machines (the\n\ files labeled \"example\" you don't have to worry about). DINO\n\ will not erase these files; in fact, it looks at some of them in\n\ order to determine the current configuration when it does an update.\n\ Once you have erased all these files, you can just start all over\n\ again\n\n\ (Hit return to continue.)", /* 52*/ " By now, you should have the impression that it is a good idea to\n\ read the DINO User's Manual. We just want to reinforce this idea.\n\ Not only is there more detailed information on use and installation\n\ in the Manual, but it also contains a comprehensive description of\n\ the DINO language and many, many example programs.\n\n\ Finally, we appreciate any feedback on how DINO works (or doesn't),\n\ how the Automated Installer worked (or didn't), and on on anything\n\ else related to DINO. You can reach us by email at\n\ \"dino@cs.colorado.edu\".\n\n\ Betty\n\ Bob\n\ Matt\n\ Rich\n\ Tom\n\n\ The DINO \"Compiler Lizards\"\n\n", /* 53*/ "\n\n Dino will set ", /* 54*/ " up for a manual installation (you will\n\ be given instructions on how to do this). Please enter\n\ the path of the directory on ", /* 55*/ " where you will want to\n\ install DINO:\n\n ==>", /* 56*/ " DINO has finished doing an update for the following machines:\n\n", /* 57*/ "\n\n DINO did not completely re-install ", /* 58*/ ". Instead, it created\n\ a directory on the sun that contains all the files needed on the\n\ parallel machine. You need to do two things: first, copy\n\ (recursively) every entry in the directory\n\n\ ", /* 59 */ "\n\n We appreciate any feedback on how DINO works (or doesn't), how\n\ the Automated Installer worked (or didn't), and on on anything\n\ else related to DINO. You can reach us by email at\n\ \"dino@cs.colorado.edu\".\n\n\ Betty\n\ Bob\n\ Matt\n\ Rich\n\ Tom\n\n\ The DINO \"Compiler Lizards\"\n\n", /* 60 */ " Dino can just update the files on the local machine (the suns\n\ with a ", /* 61 */ " architecture), or it can update all the remote\n\ parallel machines as well. You would do the former if you\n\ simply wanted to install a second sun architecture. You would\n\ do the latter in a normal full update. Do you want to install\n\ the remote parallel machines as well as the local (sun) part?", /* 62 */ " DINO has finished doing an update for the front end of the DINO\n\ compiler.\n", /* 63 */ " What is the full path name on ", /* 64 */ " for the directory which is called:\n\n ", /* 65 */ " on this machine?\n\n ==>", /* 66 */ " Note: DINO has found the directory \"tmp_mnt\" at the\n\ beginning of the path for your current directory. DINO\n\ assumes that this means that your system is using Sun's\n\ automounter and has stripped \"tmp_mnt\" off the path. If\n\ this is NOT the case, the installation will not work\n\ properly and you should contact \"dino@cs.colorado.edu\"\n\ for help.\n\n", /* 67 */ "\n\n What is the full path name for the file which is the ", /* 68 */ " simulator library? Note, that if you are on a dual\n\ architecture system (sun3/sun4), you can use \"${ARCHTYPE}\"\n\ or \"$ARCHTYPE\" as one component of the path.\n\n ==> ", /* 69 */ "\n Sorry, The Automated Installer only allows one virtual machine\n\ per remote real machine. The machine you just configured, \"", /* 70 */ "\",\n\ has the same address as an earlier machine, \"", /* 71 */ "\",\n\ If you need to install two virtual machines on the same remote\n\ parallel machine, you will have to do all but the first\n\ installation manually. Consult the Installation Section of the\n\ DINO User's Manual for more information on this.\n\n\ Enter a \"Q\" to quit The Automated Installer, or just hit\n\ return to start defining this machine over.\n\n\ ==>", /* 72 */ " The value of the environment variable \"ARCHTYPE\" should be\n\ either \"sun3\" or \"sun4\". Instead it is ", /* 73 */ " Please correct this problem and rerun the Automated Installer.\n\ See the DINO User's Manual if you need more information.\n\n", /* 74 */ " (even if the path name for that directory\n\ is different on the different machines)?" };